On x86/64 a domU kernel just sits around forever on a panic because
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Wed, 22 Mar 2006 09:38:44 +0000 (10:38 +0100)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Wed, 22 Mar 2006 09:38:44 +0000 (10:38 +0100)
the HV doesn't know it crashed.  This patch sends the signal, which
allows the kernel to be cleaned up (according to whatever guest.conf
rules). It is basically copied and pasted from the i386 branch.

From: Don Zickus
Signed-off-by: Keir Fraser <keir@xensource.com>
linux-2.6-xen-sparse/arch/x86_64/kernel/setup-xen.c

index c06c2b26a171e3e720df99f85c57c83a2eeacdf0..aa7d503a4115f376520a55375c62f0a2cad2e366 100644 (file)
@@ -93,6 +93,11 @@ EXPORT_SYMBOL(hypercall_page);
 /* Allows setting of maximum possible memory size  */
 unsigned long xen_override_max_pfn;
 
+static int xen_panic_event(struct notifier_block *, unsigned long, void *);
+static struct notifier_block xen_panic_block = {
+       xen_panic_event, NULL, 0 /* try to go last */
+};
+
 unsigned long *phys_to_machine_mapping;
 unsigned long *pfn_to_mfn_frame_list_list, *pfn_to_mfn_frame_list[512];
 
@@ -634,6 +639,9 @@ void __init setup_arch(char **cmdline_p)
        unsigned long kernel_end;
 
 #ifdef CONFIG_XEN
+       /* Register a call for panic conditions. */
+       notifier_chain_register(&panic_notifier_list, &xen_panic_block);
+
        ROOT_DEV = MKDEV(RAMDISK_MAJOR,0); 
        kernel_end = 0;         /* dummy */
        screen_info = SCREEN_INFO;
@@ -989,6 +997,17 @@ void __init setup_arch(char **cmdline_p)
 #endif /* !CONFIG_XEN */
 }
 
+#ifdef CONFIG_XEN
+static int
+xen_panic_event(struct notifier_block *this, unsigned long event, void *ptr)
+{
+       HYPERVISOR_sched_op(SCHEDOP_shutdown, SHUTDOWN_crash);
+       /* we're never actually going to get here... */
+       return NOTIFY_DONE;
+}
+#endif /* !CONFIG_XEN */
+
+
 static int __cpuinit get_model_name(struct cpuinfo_x86 *c)
 {
        unsigned int *v;